helm: add per shard backup cron jobs#4356
Merged
dkhenry merged 1 commit intovitessio:masterfrom Nov 16, 2018
Merged
Conversation
derekperkins
force-pushed
the
cronjob-backups
branch
from
929acbf to
fb706b3
Compare
Member
Author
|
@trevex Can you take a look to make sure that I used your extra flags correctly? |
Signed-off-by: Derek Perkins <derek@derekperkins.com>
derekperkins
force-pushed
the
cronjob-backups
branch
from
fb706b3 to
e050355
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This creates a native kubernetes cron job that executes according to a customer provided schedule to run backups. The schedule can be defined globally or can be overridden on a per-shard basis.
After #4333 is merged, we'll need to add the extra flags to this call as well to support encryption and any other user provided flags.Done